Understanding minor versions

Minor versions enable you to keep track of changes to a document's properties or attached files without creating new major versions during the creation or revision of the document. Minor versions can be identified by the Version number in the form of <MajorVersionNumber>.<MinorVersionNumber>, for example, 1.4.

A minor version is automatically created when:

• Most document properties are updated
• Files and URLs are added or updated

A minor version is not created when:

• Minor versions are enabled for the workspace
• Commands in the Collaboration group of the ribbon are run
• When links or subdocuments are created
• The Status property is updated

When a minor version is created, the previous version (including property values, file versions, and so on) is saved as a minor version.

Note    Only one physical copy of identical document attachment files is stored in order to preserve storage space.

Minor versions are removed when a new major version of a document is released. For example, in the following sequence of events, upon the release of version 2.1, the minor versions 1.2 and 1.3 are removed and version 1.4 is saved in the document's history data.

1. Create (1.1)
2. New version (1.2)
3. New version (1.3)
4. New version (1.4)
5. Status to Released (2.1)

Note    By default, minor version history is removed when a new version of the document is created. The can be disabled for a workspace by a system administrator.

Prior minor versions of a document are only accessible through the document's properties as described in Viewing history. Document commands such as Edit, Delete, searches and so on, are not available for prior minor versions. The property page of a prior minor version shows the property values that were set while the minor version was still active.

Note    A system administrator can reactivate a prior minor version with the Revert command. Reverting to the latest minor version enables the standard document commands.